Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

community,labels,sig-list: update/remove labels #348

Merged
merged 1 commit into from
Nov 7, 2024

Conversation

dhiller
Copy link
Contributor

@dhiller dhiller commented Nov 6, 2024

What this PR does / why we need it:

Updates labels on sigs.yaml to the ones that exist and are used, where others that don't exist are removed.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

/kind cleanup

/cc @aburdenthehand

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

Release note:


@kubevirt-bot kubevirt-bot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/S labels Nov 6, 2024
sig-list.md Outdated Show resolved Hide resolved
Updates labels on sigs to the ones that exist and are used, where others
that don't exist are removed.

Signed-off-by: Daniel Hiller <[email protected]>
@dhiller
Copy link
Contributor Author

dhiller commented Nov 6, 2024

@aburdenthehand added sig/scale label, PTAL, thanks!

@aburdenthehand
Copy link
Member

/lgtm
Thanks @dhiller :D

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Nov 6, 2024
@dhiller
Copy link
Contributor Author

dhiller commented Nov 7, 2024

FYI @awels @EdDev @alaypatel07

@awels
Copy link
Member

awels commented Nov 7, 2024

/lgtm

Copy link
Contributor

@jean-edouard jean-edouard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/hold
Looks good, just found one weird thing, see in-line, feel free to unhold.

@@ -21,7 +21,7 @@ Each group's material is in its subdirectory in this project.

| Name | Label [1] | Chairs [2] | Contact | Meetings |
|------|-----------|---------|---------|----------|
|[KubeVirt Community](kubevirt-community/charter.md) |[kubevirt-community](https://github.com/kubevirt/kubevirt/labels/kubevirt-community)|<ol></ol> |[Slack](virtualization)<br/> [Mailing List](https://groups.google.com/forum/#!forum/kubevirt-dev) |<ul><li>Regular KubeVirt Community Meeting: [ Wednesday at 15:00 UTC (weekly) ](https://zoom.us/j/92221936273)</li></ul> |
|[KubeVirt Community](kubevirt-community/charter.md) |[](https://github.com/kubevirt/kubevirt/labels/)|<ol></ol> |[Slack](virtualization)<br/> [Mailing List](https://groups.google.com/forum/#!forum/kubevirt-dev) |<ul><li>Regular KubeVirt Community Meeting: [ Wednesday at 15:00 UTC (weekly) ](https://zoom.us/j/92221936273)</li></ul> |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why? That makes the link invisible

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's right to do this since the label kubevirt-community doesn't exist: https://github.com/kubevirt/project-infra/blob/main/docs/labels.md
We can argue about the flaw in the template leading to these empty edgy braces, but I think that's just a minor issue, which we can follow up on. WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer if the generator could put nothing there instead of a broken and unclickable link, but if it's too much work then whatever.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not saying it's too much work - I have PR #346 where I am working on (which you already reviewed) and where I'll add the change.

@kubevirt-bot kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 7, 2024
@kubevirt-bot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jean-edouard

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 7, 2024
@dhiller
Copy link
Contributor Author

dhiller commented Nov 7, 2024

@jean-edouard I am going to remove the hold here, and rebase the changes inside the other PR if you don't mind.

@dhiller
Copy link
Contributor Author

dhiller commented Nov 7, 2024

/unhold

@kubevirt-bot kubevirt-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 7, 2024
@kubevirt-bot kubevirt-bot merged commit cf63b75 into kubevirt:main Nov 7, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants